4. Issues found during testing

These included:

Missing timezones in ICS for single events.

When the recurrence rule doesn’t match the first start then some services silently move the first start to the first actual occurrence (which seems reasonable)

Moving a recurring instance into a different day did not work correctly.

Timezone customization is not set for events (at least recurring) sent through iMIP (although the timezone is saved).

Some clients were mishandling sequence numbers

Create a recurring event in the future, save and send invitations

• “Add to Calendar” set a response, e.g. Yes

• Move an exception to a different time (again, send updates)

• “Update Calendar” set a response, e.g. Maybe

• Result: the response is discarded as outdated

Some servers don’t send invitations for past events even when the user is explicitly asked whether to send or not and says yes.

There were problems with autodiscovery

Some issues discovered and questions about Android clients:

• may only sync 1 year of data

• attachments first appear and then disappear again

• Is CalDAV syncing support in the future?

• Android is missing new features or bugs, e.g.:

  • bad recurrence expansions

  • empty recurring events (when all instances are cancelled)

Client iMip bug: invitations to single instances of a recurring event are not handled properly

Server iMip bug: Have a recurring event with one exception moved, then invite an attendee — the invitation only contains the series but not the exception

An interesting fact was noted: for recurring events where the recurrence doesn’t match the start date — between Apple, FastMail, Google and Open-Xchange these are all expanded differently (3 different behaviors).